Add initial support for Gaisler-BCC with Sparc #8285
Conversation
|
retest this please |
There was a problem hiding this comment.
from PRB-multi-test-script:
[check-source-text] [2 of 7] [wolfssl]
autogen.sh wolfssl... real 0m14.913s user 0m8.756s sys 0m0.214s
configure... real 0m21.143s user 0m9.405s sys 0m2.425s
unrecognized macros used:
__sparc
add well-formed but unknown macros to /tmp/workspace/PRB-multi-test-script/wolfssl/.wolfssl_known_macro_extras.
(it means .wolfssl_known_macro_extras at the top of the repo.)
There's also an error in PRB-fips-read-config but I think it's a false positive.
|
Dang, when it kept failing I thought that might be the case, but I didn't see it in the Jenkins output. I'll fix ASAP. |
LinuxJedi
force-pushed
the
gaisler
branch
2 times, most recently
from
b699df0 to
231cea3
Compare
Slight modifications and documentation to get wolfSSL working with Gaisler Sparc CPUs and their cross-compilers.
|
@douzzer I fixed that problem. Any idea why Jenkins is still failing? I don't see it in the log. |
|
retest this please ( |
|
By the way, glibc no longer has support for pre-v8 sparc, and trying to build a toolchain for TL;DR: Currently we have sparc64 testing in the nightly (just basic P.s. interestingly, on sparc64, we have to disable sakke to get it to pass, otherwise |
Description
Slight modifications and documentation to get wolfSSL working with Gaisler Sparc CPUs and their cross-compilers.
Testing
Using TSIM3 LEON3 evaluation version (https://www.gaisler.com/index.php/downloads/simulators).
Checklist